Description

afterthought:
The aim of this was to cover some segmentation fault.
This does not solve those segmentation faults
But I think that that is due some problems that cam from what happen after error is used. I just solved the no badge problem in some part of the manual, but some pages like the one about the ... now it should render correcly, or at leas running an example with standalone things when you do not care about the status badge

In #1183 I randomly discovered a sigsegv when running gen_example on plumed tools.

It looked like the "nobadge" status was missing from the options when creating a badge, now it displays a in that case.

"nobadge" looks like it is the default status when gen_example is called with no arguments, so I do not know it this is the correct solution (but

Target release

I would like my code to appear in release v2.10

Type of contribution

• changes to code or doc authored by PLUMED developers, or additions of code in the core or within the default modules
• changes to a module not authored by you
• new module contribution or edit of a module authored by you

Copyright

• I agree to transfer the copyright of the code I have written to the PLUMED developers or to the author of the code I am modifying.

• the module I added or modified contains a COPYRIGHT file with the correct license information. Code should be released under an open source license. I also used the command cd src && ./header.sh mymodulename in order to make sure the headers of the module are correct.

Tests

• I added a new regtest or modified an existing regtest to validate my changes.
• I verified that all regtests are passed successfully on GitHub Actions.